Hi David,

KFLOP saves the Soft Limits as a single precision floating point number (almost 7 digits of precision).  Exponents for single precision numbers are limited to ~38.  50 would be an invalid number and isn't handled correctly.

Probably a billion counts would be enough in your case.  So set to 1e9 and -1e9.

Regards

TK

Group: DynoMotion	Message: 10952	From: Tom Kerekes	Date: 1/29/2015
Subject: Re: Soft Limits Programming Issue

Hi David, heh heh 10^50 counts would probably be in the next Universe over :} TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Thursday, January 29, 2015 10:20 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, I knew it would be something simple and yes, I could manage with only a billion.  :} Thanks again, David. On 1/29/2015 1:16 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, KFLOP saves the Soft Limits as a single precision floating point number (almost 7 digits of precision).  Exponents for single precision numbers are limited to ~38.  50 would be an invalid number and isn't handled correctly. Probably a billion counts would be enough in your case.  So set to 1e9 and -1e9. Regards TK Group: DynoMotion Message: 10953 From: David Stevenson Date: 1/29/2015 Subject: Re: Soft Limits Programming Issue Hi Tom, I'm pretty sure I would have a ballscrew issue before a soft limit one, in that case.  :oO Anyhow, I changed the softlimits on that axis (Z) and also A to +/-1e+009 (the others were at +/-1e+030), but still can't shake that error. Did full restart, power down, etc. Does it make a difference with A and Z being stepper motors? X and Y in this case are servos and A and Z are steppers. Thanks, David. On 1/29/2015 1:26 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, heh heh 10^50 counts would probably be in the next Universe over :} TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Thursday, January 29, 2015 10:20 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, I knew it would be something simple and yes, I could manage with only a billion.  :} Thanks again, David. On 1/29/2015 1:16 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, KFLOP saves the Soft Limits as a single precision floating point number (almost 7 digits of precision).  Exponents for single precision numbers are limited to ~38.  50 would be an invalid number and isn't handled correctly. Probably a billion counts would be enough in your case.  So set to 1e9 and -1e9. Regards TK Group: DynoMotion Message: 10954 From: Tom Kerekes Date: 1/29/2015 Subject: Re: Soft Limits Programming Issue Hi David, Please post your Init C file for us to look at. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Thursday, January 29, 2015 1:33 PM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, I'm pretty sure I would have a ballscrew issue before a soft limit one, in that case.  :oO Anyhow, I changed the softlimits on that axis (Z) and also A to +/-1e+009 (the others were at +/-1e+030), but still can't shake that error. Did full restart, power down, etc. Does it make a difference with A and Z being stepper motors? X and Y in this case are servos and A and Z are steppers. Thanks, David. On 1/29/2015 1:26 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, heh heh 10^50 counts would probably be in the next Universe over :} TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Thursday, January 29, 2015 10:20 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, I knew it would be something simple and yes, I could manage with only a billion.  :} Thanks again, David. On 1/29/2015 1:16 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, KFLOP saves the Soft Limits as a single precision floating point number (almost 7 digits of precision).  Exponents for single precision numbers are limited to ~38.  50 would be an invalid number and isn't handled correctly. Probably a billion counts would be enough in your case.  So set to 1e9 and -1e9. Regards TK Group: DynoMotion Message: 10955 From: David Stevenson Date: 1/29/2015 Subject: Re: Soft Limits Programming Issue Attachments : DavidsInit-10955.c Hi Tom, Here you go. Enjoy! Best regards, David. On 1/29/2015 5:55 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, Please post your Init C file for us to look at. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Thursday, January 29, 2015 1:33 PM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, I'm pretty sure I would have a ballscrew issue before a soft limit one, in that case.  :oO Anyhow, I changed the softlimits on that axis (Z) and also A to +/-1e+009 (the others were at +/-1e+030), but still can't shake that error. Did full restart, power down, etc. Does it make a difference with A and Z being stepper motors? X and Y in this case are servos and A and Z are steppers. Thanks, David. On 1/29/2015 1:26 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, heh heh 10^50 counts would probably be in the next Universe over :} TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Thursday, January 29, 2015 10:20 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, I knew it would be something simple and yes, I could manage with only a billion.  :} Thanks again, David. On 1/29/2015 1:16 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, KFLOP saves the Soft Limits as a single precision floating point number (almost 7 digits of precision).  Exponents for single precision numbers are limited to ~38.  50 would be an invalid number and isn't handled correctly. Probably a billion counts would be enough in your case.  So set to 1e9 and -1e9. Regards TK Group: DynoMotion Message: 10956 From: Tom Kerekes Date: 1/30/2015 Subject: Re: Soft Limits Programming Issue Hi David, The soft limits all look correct to me.  Did you ever resolve this?  Are you sure you are really using this file?  As a sanity check I sometimes rename the file I think is being used.  If I then get an error I know it really is the one being used. Is your homing routine changing the Soft Limits? After you get the +Z Soft Limit error you might also "Upload" the Z Axis to KMotion.exe to check the Soft Limit + value is as expected on the Screen. HTH Regards TK Group: DynoMotion Message: 10958 From: David Stevenson Date: 1/30/2015 Subject: Re: Soft Limits Programming Issue Hi Tom, I haven't resolved this. I renamed the file to post, but I am sure it's the one running. I will triple check using your suggestion. That file is also the homing routine. I will try the upload suggestion too. Thank you, David. On 1/30/2015 2:26 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, The soft limits all look correct to me.  Did you ever resolve this?  Are you sure you are really using this file?  As a sanity check I sometimes rename the file I think is being used.  If I then get an error I know it really is the one being used. Is your homing routine changing the Soft Limits? After you get the +Z Soft Limit error you might also "Upload" the Z Axis to KMotion.exe to check the Soft Limit + value is as expected on the Screen. HTH Regards TK Group: DynoMotion Message: 10962 From: David Stevenson Date: 1/30/2015 Subject: Re: Soft Limits Programming Issue Attachments : Screenshot (1)-10962.png Hi Tom, I did confirm that the file I posted was indeed the one initializing the machine. Once the machine homed I uploaded the Z axis and the soft limits were as expected. I am attaching a screenshot of the error message in case I didn't describe it appropriately previously. I though it may give some clues. Thank you, David. On 1/30/2015 2:26 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, The soft limits all look correct to me.  Did you ever resolve this?  Are you sure you are really using this file?  As a sanity check I sometimes rename the file I think is being used.  If I then get an error I know it really is the one being used. Is your homing routine changing the Soft Limits? After you get the +Z Soft Limit error you might also "Upload" the Z Axis to KMotion.exe to check the Soft Limit + value is as expected on the Screen. HTH Regards TK Group: DynoMotion Message: 10977 From: Tom Kerekes Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue [1 Attachment] Attachments : Hi David, I'm not able to reproduce the problem.  Could you possibly have a huge Z offset of some type (Tool length, Fixture, or axis)? If you select to display Machine Coordinates do the DRO's remain zero? Anything odd in the Tool Table or Offsets Table? I've attached your Init file modified to work without any hardware.  Please try it so we are both doing exactly the same thing.  Power up KFLOP with all motor power off (and even disconnected if necessary).  Initialize.  Then run KMotionCNC, Load box10.ngc exmple.  Then Cycle Start. Do you get any error? Regards TK Group: DynoMotion Message: 10982 From: David Stevenson Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue Hi David, Thanks for letting me know.  We must have a bug regarding negative resolutions. The total +5V power for KFLOP + 2 SnapAmps should be certainly less than 2 Amps. Regards TK Attachments : Screenshot (2)-10982.png Hi Tom, I double checked and there are no offsets set. The DRO's also do not change when Machine Coordinates are selected. The only tool offsets are the example ones in KMotionCNC. I disconnected the drives and ran your file in KMotion. It did not complete within, about 5 minutes, so I halted it. I did take a screenshot before I halted it, so you could see it. Thanks for your help with this, David. On 2/2/2015 11:35 AM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I'm not able to reproduce the problem.  Could you possibly have a huge Z offset of some type (Tool length, Fixture, or axis)? If you select to display Machine Coordinates do the DRO's remain zero? Anything odd in the Tool Table or Offsets Table? I've attached your Init file modified to work without any hardware.  Please try it so we are both doing exactly the same thing.  Power up KFLOP with all motor power off (and even disconnected if necessary).  Initialize.  Then run KMotionCNC, Load box10.ngc exmple.  Then Cycle Start. Do you get any error? Regards TK Group: DynoMotion Message: 10996 From: Tom Kerekes Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue [1 Attachment] Group:Message:From:Date:Subject: Hi Tom, Your thinking on the trigger was right on. I changed the resolution to a positive value and away it went. I was sure I had tried that along the way. Thank you for your patience and guidance with that. On another note, what is the normal 5V power consumption for a KFlop with 2 SnapAmps? My 5V power supply seems to be getting warm. Regards, David. On 2/5/2015 6:28 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, InitKStep3Axis.c program is intentionally written to never complete (it watches for motion and enables/disables KSTEP to reduce heat when idle).  So it is normal that it doesn't complete.  Just go ahead and run the GCode in KMotionCNC. No it will not work with SnapAmps.  The idea is to test with no hardware connected at all so it doesn't matter what hardware you don't have. I'm thinking the issue is triggered by the negative Trajectory Planner resolution.  Please change your Trajectory Planner configuration to a positive number to see if that makes the problem go away.  You can reverse a SnapAmp Micro Stepper Axis by changing the sign of the invDistPerCycle parameter. Regards TK Hi David, The Console Screen indicates a Following Error on Axis 0.  Could you analyze the reason? Also in the GCode the error seems to occur after your M101.  What does your M101 do?  Does it have the error with it removed? Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Monday, February 2, 2015 9:42 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue [1 Attachment]   [Attachment(s) from David Stevenson included below] Hi Tom, I double checked and there are no offsets set. The DRO's also do not change when Machine Coordinates are selected. The only tool offsets are the example ones in KMotionCNC. I disconnected the drives and ran your file in KMotion. It did not complete within, about 5 minutes, so I halted it. I did take a screenshot before I halted it, so you could see it. Thanks for your help with this, David. On 2/2/2015 11:35 AM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I'm not able to reproduce the problem.  Could you possibly have a huge Z offset of some type (Tool length, Fixture, or axis)? If you select to display Machine Coordinates do the DRO's remain zero? Anything odd in the Tool Table or Offsets Table? I've attached your Init file modified to work without any hardware.  Please try it so we are both doing exactly the same thing.  Power up KFLOP with all motor power off (and even disconnected if necessary).  Initialize.  Then run KMotionCNC, Load box10.ngc exmple.  Then Cycle Start. Do you get any error? Regards TK Group: DynoMotion Message: 10999 From: David Stevenson Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue Group:Message:From:Date:Subject: Hi Tom, My version of the file doesn't present that following error on axis 0. M101 sets a bit to turn on a stack light. I will try with it removed, but it is a standard M thing I put in each machine. Thanks, David. On 2/2/2015 6:55 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, The Console Screen indicates a Following Error on Axis 0.  Could you analyze the reason? Also in the GCode the error seems to occur after your M101.  What does your M101 do?  Does it have the error with it removed? Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Monday, February 2, 2015 9:42 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue [1 Attachment]   [Attachment(s) from David Stevenson included below] Hi Tom, I double checked and there are no offsets set. The DRO's also do not change when Machine Coordinates are selected. The only tool offsets are the example ones in KMotionCNC. I disconnected the drives and ran your file in KMotion. It did not complete within, about 5 minutes, so I halted it. I did take a screenshot before I halted it, so you could see it. Thanks for your help with this, David. On 2/2/2015 11:35 AM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I'm not able to reproduce the problem.  Could you possibly have a huge Z offset of some type (Tool length, Fixture, or axis)? If you select to display Machine Coordinates do the DRO's remain zero? Anything odd in the Tool Table or Offsets Table? I've attached your Init file modified to work without any hardware.  Please try it so we are both doing exactly the same thing.  Power up KFLOP with all motor power off (and even disconnected if necessary).  Initialize.  Then run KMotionCNC, Load box10.ngc exmple.  Then Cycle Start. Do you get any error? Regards TK Group: DynoMotion Message: 11000 From: Tom Kerekes Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue Hi Tom, I forgot about the SnapAmps being plugged in, so I disconnected them and the gcode seems to work fine (box10.ngc). First thing tomorrow I will try the original init and configuration with the trajectory planner changed to a positive value. I think I had tried that previously, but I will confirm. Thank you, David. On 2/5/2015 6:28 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, InitKStep3Axis.c program is intentionally written to never complete (it watches for motion and enables/disables KSTEP to reduce heat when idle).  So it is normal that it doesn't complete.  Just go ahead and run the GCode in KMotionCNC. No it will not work with SnapAmps.  The idea is to test with no hardware connected at all so it doesn't matter what hardware you don't have. I'm thinking the issue is triggered by the negative Trajectory Planner resolution.  Please change your Trajectory Planner configuration to a positive number to see if that makes the problem go away.  You can reverse a SnapAmp Micro Stepper Axis by changing the sign of the invDistPerCycle parameter. Regards TK Hi David, On my system with no hardware the program completes with no following error. You said on your system the program never completes and the screen shot you sent showed a following error on the Console Screen so I assumed that was related and might be the reason for it not completing. In any case please figure out why the program doesn't complete for you.  You can do that by looking at the Console to see which of the messages in the program get printed to the console and which don't.  You might want to add more printf's to narrow it down further if necessary.  But avoid putting message inside loop or you wil flood the Console with messages. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Monday, February 2, 2015 4:27 PM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, My version of the file doesn't present that following error on axis 0. M101 sets a bit to turn on a stack light. I will try with it removed, but it is a standard M thing I put in each machine. Thanks, David. On 2/2/2015 6:55 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, The Console Screen indicates a Following Error on Axis 0.  Could you analyze the reason? Also in the GCode the error seems to occur after your M101.  What does your M101 do?  Does it have the error with it removed? Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Monday, February 2, 2015 9:42 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue [1 Attachment]   [Attachment(s) from David Stevenson included below] Hi Tom, I double checked and there are no offsets set. The DRO's also do not change when Machine Coordinates are selected. The only tool offsets are the example ones in KMotionCNC. I disconnected the drives and ran your file in KMotion. It did not complete within, about 5 minutes, so I halted it. I did take a screenshot before I halted it, so you could see it. Thanks for your help with this, David. On 2/2/2015 11:35 AM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I'm not able to reproduce the problem.  Could you possibly have a huge Z offset of some type (Tool length, Fixture, or axis)? If you select to display Machine Coordinates do the DRO's remain zero? Anything odd in the Tool Table or Offsets Table? I've attached your Init file modified to work without any hardware.  Please try it so we are both doing exactly the same thing.  Power up KFLOP with all motor power off (and even disconnected if necessary).  Initialize.  Then run KMotionCNC, Load box10.ngc exmple.  Then Cycle Start. Do you get any error? Regards TK Group: DynoMotion Message: 11003 From: David Stevenson Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue Group:Message:From:Date:Subject: Hi David, InitKStep3Axis.c program is intentionally written to never complete (it watches for motion and enables/disables KSTEP to reduce heat when idle).  So it is normal that it doesn't complete.  Just go ahead and run the GCode in KMotionCNC. No it will not work with SnapAmps.  The idea is to test with no hardware connected at all so it doesn't matter what hardware you don't have. I'm thinking the issue is triggered by the negative Trajectory Planner resolution.  Please change your Trajectory Planner configuration to a positive number to see if that makes the problem go away.  You can reverse a SnapAmp Micro Stepper Axis by changing the sign of the invDistPerCycle parameter. Regards TK Hi Tom, When I ran the file, the 4 drive motors were disconnected. I suspect the following error is because the file is expecting the motors are moving, but the encoders, which are still connected, don't show any movement. Does that make sense? The last message that came up was the following error. I then gave KMotion a few more minutes until it became obvious that it was not progressing. Regards, David. On 2/2/2015 9:03 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, On my system with no hardware the program completes with no following error. You said on your system the program never completes and the screen shot you sent showed a following error on the Console Screen so I assumed that was related and might be the reason for it not completing. In any case please figure out why the program doesn't complete for you.  You can do that by looking at the Console to see which of the messages in the program get printed to the console and which don't.  You might want to add more printf's to narrow it down further if necessary.  But avoid putting message inside loop or you wil flood the Console with messages. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Monday, February 2, 2015 4:27 PM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, My version of the file doesn't present that following error on axis 0. M101 sets a bit to turn on a stack light. I will try with it removed, but it is a standard M thing I put in each machine. Thanks, David. On 2/2/2015 6:55 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, The Console Screen indicates a Following Error on Axis 0.  Could you analyze the reason? Also in the GCode the error seems to occur after your M101.  What does your M101 do?  Does it have the error with it removed? Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Monday, February 2, 2015 9:42 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue [1 Attachment]   [Attachment(s) from David Stevenson included below] Hi Tom, I double checked and there are no offsets set. The DRO's also do not change when Machine Coordinates are selected. The only tool offsets are the example ones in KMotionCNC. I disconnected the drives and ran your file in KMotion. It did not complete within, about 5 minutes, so I halted it. I did take a screenshot before I halted it, so you could see it. Thanks for your help with this, David. On 2/2/2015 11:35 AM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I'm not able to reproduce the problem.  Could you possibly have a huge Z offset of some type (Tool length, Fixture, or axis)? If you select to display Machine Coordinates do the DRO's remain zero? Anything odd in the Tool Table or Offsets Table? I've attached your Init file modified to work without any hardware.  Please try it so we are both doing exactly the same thing.  Power up KFLOP with all motor power off (and even disconnected if necessary).  Initialize.  Then run KMotionCNC, Load box10.ngc exmple.  Then Cycle Start. Do you get any error? Regards TK Group: DynoMotion Message: 11004 From: Tom Kerekes Date: 2/2/2015 Subject: Re: Soft Limits Programming Issue Group:Message:From:Date:Subject: Hi David, I thought you said your "My version of the file doesn't present that following error on axis 0." Now you are saying it does?  It seems we aren't communicating. The Max allowed following error is being set to a huge value (1000000000).  So I wouldn't expect a following error even if the motors were disconnected. Please do some logical investigation.  If it displays Following error Axis:0 then open the Axis Screen to see the difference between the Position and the Destination of Axis 0. Regards TK Group: DynoMotion Message: 11009 From: David Stevenson Date: 2/3/2015 Subject: Re: Soft Limits Programming Issue Hi Tom, I did a fresh install, as you requested, but the init file doesn't complete. Are you sure it works without a Kstep card? My system has SnapAmps. Regards, David. On 2/5/2015 1:50 PM, David Stevenson [DynoMotion] wrote: david.m.stevenson@...   Hi Tom, I have 2 machines with the exact same computers. The machine causing the problem has the 2 extra stepper motors on axis Z and A. The machine without problems has 2 BLDC servos. Other than that, they have the same electrical systems, except for the double SnapAmp on the one with the extra motors. See the attached screenshot of the TP settings of the problem machine. I will a fresh install using the settings suggested. Thank you, David. On 2/5/2015 1:15 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, Strange with regard that you are doing nearly everything exactly as I am and yet you get the error and I (or others) don't seem to have any issue.  I wonder if there is something specific about your PC ? We still may have different Trajectory Planner settings.  I suppose that may be it.  Something like a small or near zero resolution would map a position of a few counts to a huge distance.  What are they? As a sanity check, check if KMotionCNC works on your system with no errors with a fresh install, no KFLOP Connections (other than USB), all default settings, initialized with the Example \KStep\InitKStep3Axis.c  This is an open loop configuration that will work with no hardware at all. If that doesn't work it would indicate something on your computer. If that does work, please proceed step-by-step migrating to your configuration to determine which step causes the issue to arise.  Regards TK Hi Tom, The davidsinit.c file, with the motors connected, does not have a following error. Your modified file, which you instructed me to run with the motors unplugged, generates the following error. The file calls for the axis to move until it sees a limit signal. In my illogical thinking, I see that the axis is going to continuing to expect movement until the cows come home, but the limit will never signal. Would this not eventually generate a following problem? Counts are 254000/inch. Not a problem. I'll get to the bottom of it. Regards, David. On 2/2/2015 9:40 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I thought you said your "My version of the file doesn't present that following error on axis 0." Now you are saying it does?  It seems we aren't communicating. The Max allowed following error is being set to a huge value (1000000000).  So I wouldn't expect a following error even if the motors were disconnected. Please do some logical investigation.  If it displays Following error Axis:0 then open the Axis Screen to see the difference between the Position and the Destination of Axis 0. Regards TK Group: DynoMotion Message: 11014 From: Tom Kerekes Date: 2/3/2015 Subject: Re: Soft Limits Programming Issue Group:Message:From:Date:Subject: Attachments : Screenshot (9)-11030.png Hi Tom, I have 2 machines with the exact same computers. The machine causing the problem has the 2 extra stepper motors on axis Z and A. The machine without problems has 2 BLDC servos. Other than that, they have the same electrical systems, except for the double SnapAmp on the one with the extra motors. See the attached screenshot of the TP settings of the problem machine. I will a fresh install using the settings suggested. Thank you, David. On 2/5/2015 1:15 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, Strange with regard that you are doing nearly everything exactly as I am and yet you get the error and I (or others) don't seem to have any issue.  I wonder if there is something specific about your PC ? We still may have different Trajectory Planner settings.  I suppose that may be it.  Something like a small or near zero resolution would map a position of a few counts to a huge distance.  What are they? As a sanity check, check if KMotionCNC works on your system with no errors with a fresh install, no KFLOP Connections (other than USB), all default settings, initialized with the Example \KStep\InitKStep3Axis.c  This is an open loop configuration that will work with no hardware at all. If that doesn't work it would indicate something on your computer. If that does work, please proceed step-by-step migrating to your configuration to determine which step causes the issue to arise.  Regards TK Hi David, I attempted to change your code to never wait for anything forever.  You might look at the changes I made.  I changed things like:         if (ReadBit(66))  // check for index mark to         if (ReadBit(66)||1)  // check for index mark This translates to: if bit66 or true = always true So all the limits and such should be faked out and signal immediately. I may have missed someplace that waits for something.  That is why I was hoping you would determine exactly how far through the program it was getting. Very strange that it generates a following error for you.  That would be a big clue and somehow having a huge position error would explain a soft limit error.  So again please look at the Axis Screen to see why on your system there is a following error. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Tuesday, February 3, 2015 3:26 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, The davidsinit.c file, with the motors connected, does not have a following error. Your modified file, which you instructed me to run with the motors unplugged, generates the following error. The file calls for the axis to move until it sees a limit signal. In my illogical thinking, I see that the axis is going to continuing to expect movement until the cows come home, but the limit will never signal. Would this not eventually generate a following problem? Counts are 254000/inch. Not a problem. I'll get to the bottom of it. Regards, David. On 2/2/2015 9:40 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I thought you said your "My version of the file doesn't present that following error on axis 0." Now you are saying it does?  It seems we aren't communicating. The Max allowed following error is being set to a huge value (1000000000).  So I wouldn't expect a following error even if the motors were disconnected. Please do some logical investigation.  If it displays Following error Axis:0 then open the Axis Screen to see the difference between the Position and the Destination of Axis 0. Regards TK Group: DynoMotion Message: 11023 From: David Stevenson Date: 2/4/2015 Subject: Re: Soft Limits Programming Issue Group:Message:From:Date:Subject: Hi Tom, The first step of the homing sequence is waiting for the limit to go off as the 0 axis retracts. I confirmed on the axis screen that the destination counts up to the following error limit and then faults because the position is not changing. If you could help me with what the limit override is I will give it another try. Regards, David. On 2/3/2015 2:44 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I attempted to change your code to never wait for anything forever.  You might look at the changes I made.  I changed things like:         if (ReadBit(66))  // check for index mark to         if (ReadBit(66)||1)  // check for index mark This translates to: if bit66 or true = always true So all the limits and such should be faked out and signal immediately. I may have missed someplace that waits for something.  That is why I was hoping you would determine exactly how far through the program it was getting. Very strange that it generates a following error for you.  That would be a big clue and somehow having a huge position error would explain a soft limit error.  So again please look at the Axis Screen to see why on your system there is a following error. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Tuesday, February 3, 2015 3:26 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, The davidsinit.c file, with the motors connected, does not have a following error. Your modified file, which you instructed me to run with the motors unplugged, generates the following error. The file calls for the axis to move until it sees a limit signal. In my illogical thinking, I see that the axis is going to continuing to expect movement until the cows come home, but the limit will never signal. Would this not eventually generate a following problem? Counts are 254000/inch. Not a problem. I'll get to the bottom of it. Regards, David. On 2/2/2015 9:40 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I thought you said your "My version of the file doesn't present that following error on axis 0." Now you are saying it does?  It seems we aren't communicating. The Max allowed following error is being set to a huge value (1000000000).  So I wouldn't expect a following error even if the motors were disconnected. Please do some logical investigation.  If it displays Following error Axis:0 then open the Axis Screen to see the difference between the Position and the Destination of Axis 0. Regards TK Group: DynoMotion Message: 11025 From: Tom Kerekes Date: 2/4/2015 Subject: Re: Soft Limits Programming Issue Hi David, Strange with regard that you are doing nearly everything exactly as I am and yet you get the error and I (or others) don't seem to have any issue.  I wonder if there is something specific about your PC ? We still may have different Trajectory Planner settings.  I suppose that may be it.  Something like a small or near zero resolution would map a position of a few counts to a huge distance.  What are they? As a sanity check, check if KMotionCNC works on your system with no errors with a fresh install, no KFLOP Connections (other than USB), all default settings, initialized with the Example \KStep\InitKStep3Axis.c  This is an open loop configuration that will work with no hardware at all. If that doesn't work it would indicate something on your computer. If that does work, please proceed step-by-step migrating to your configuration to determine which step causes the issue to arise.  Regards TK Hi David, Ahh yes I forgot those while loops:     while (ReadBit(75));                            // loop until IO bit goes low (Y axis -) and     while (ReadBit(73)) ;                   // loop until IO bit goes low (X-axis +) remove them Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Wednesday, February 4, 2015 12:17 PM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, The first step of the homing sequence is waiting for the limit to go off as the 0 axis retracts. I confirmed on the axis screen that the destination counts up to the following error limit and then faults because the position is not changing. If you could help me with what the limit override is I will give it another try. Regards, David. On 2/3/2015 2:44 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I attempted to change your code to never wait for anything forever.  You might look at the changes I made.  I changed things like:         if (ReadBit(66))  // check for index mark to         if (ReadBit(66)||1)  // check for index mark This translates to: if bit66 or true = always true So all the limits and such should be faked out and signal immediately. I may have missed someplace that waits for something.  That is why I was hoping you would determine exactly how far through the program it was getting. Very strange that it generates a following error for you.  That would be a big clue and somehow having a huge position error would explain a soft limit error.  So again please look at the Axis Screen to see why on your system there is a following error. Regards TK From: "David Stevenson david.m.stevenson@... [DynoMotion]" <DynoMotion@yahoogroups.com> To: DynoMotion@yahoogroups.com Sent: Tuesday, February 3, 2015 3:26 AM Subject: Re: [DynoMotion] Soft Limits Programming Issue   Hi Tom, The davidsinit.c file, with the motors connected, does not have a following error. Your modified file, which you instructed me to run with the motors unplugged, generates the following error. The file calls for the axis to move until it sees a limit signal. In my illogical thinking, I see that the axis is going to continuing to expect movement until the cows come home, but the limit will never signal. Would this not eventually generate a following problem? Counts are 254000/inch. Not a problem. I'll get to the bottom of it. Regards, David. On 2/2/2015 9:40 PM, Tom Kerekes tk@... [DynoMotion] wrote:   Hi David, I thought you said your "My version of the file doesn't present that following error on axis 0." Now you are saying it does?  It seems we aren't communicating. The Max allowed following error is being set to a huge value (1000000000).  So I wouldn't expect a following error even if the motors were disconnected. Please do some logical investigation.  If it displays Following error Axis:0 then open the Axis Screen to see the difference between the Position and the Destination of Axis 0. Regards TK Group: DynoMotion Message: 11026 From: David Stevenson Date: 2/4/2015 Subject: Re: Soft Limits Programming Issue Group:Message:From:Date:Subject: Hi Tom, I removed the loops, the program completed, I launched KMotionCNC and tried to run box10.ngc. It gave the same error message. The strange thing is the jog buttons work for all 4 axis, but if I try a gcode program or the command line at the bottom of KMotionCNC, I get the soft limit error. I thought it might have been a corrupt file or something along those lines, so I re-installed v433k, but it didn't make any difference. Regards, David. On 2/4/2015 9:14 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, Ahh yes I forgot those while loops:     while (ReadBit(75));                            // loop until IO bit goes low (Y axis -) and     while (ReadBit(73)) ;                   // loop until IO bit goes low (X-axis +) remove them Regards TK "David Stevenson [DynoMotion]" Wednesday, February 4, 2015 12:17 PM Re: [DynoMotion] Soft Limits Programming Issue From:david.m.stevenson@...<DynoMotion@yahoogroups.com> To:DynoMotion@yahoogroups.com Sent: Subject:   Hi Tom, The first step of the homing sequence is waiting for the limit to go off as the 0 axis retracts. I confirmed on the axis screen that the destination counts up to the following error limit and then faults because the position is not changing. If you could help me with what the limit override is I will give it another try. Regards, David. On 2/3/2015 2:44 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, I attempted to change your code to never wait for anything forever.  You might look at the changes I made.  I changed things like:         if (ReadBit(66))  // check for index mark to         if (ReadBit(66)||1)  // check for index mark This translates to: if bit66 or true = always true So all the limits and such should be faked out and signal immediately. I may have missed someplace that waits for something.  That is why I was hoping you would determine exactly how far through the program it was getting. Very strange that it generates a following error for you.  That would be a big clue and somehow having a huge position error would explain a soft limit error.  So again please look at the Axis Screen to see why on your system there is a following error. Regards TK "David Stevenson [DynoMotion]" Tuesday, February 3, 2015 3:26 AM Re: [DynoMotion] Soft Limits Programming Issue From:david.m.stevenson@...<DynoMotion@yahoogroups.com> To:DynoMotion@yahoogroups.com Sent: Subject:   Hi Tom, The davidsinit.c file, with the motors connected, does not have a following error. Your modified file, which you instructed me to run with the motors unplugged, generates the following error. The file calls for the axis to move until it sees a limit signal. In my illogical thinking, I see that the axis is going to continuing to expect movement until the cows come home, but the limit will never signal. Would this not eventually generate a following problem? Counts are 254000/inch. Not a problem. I'll get to the bottom of it. Regards, David. On 2/2/2015 9:40 PM, Tom Kerekes [DynoMotion] wrote: tk@...   Hi David, I thought you said your "My version of the file doesn't present that following error on axis 0." Now you are saying it does?  It seems we aren't communicating. The Max allowed following error is being set to a huge value (1000000000).  So I wouldn't expect a following error even if the motors were disconnected. Please do some logical investigation.  If it displays Following error Axis:0 then open the Axis Screen to see the difference between the Position and the Destination of Axis 0. Regards TK DynoMotion 11029 Tom Kerekes 2/5/2015 Re: Soft Limits Programming Issue DynoMotion 11030 David Stevenson 2/5/2015 Re: Soft Limits Programming Issue DynoMotion 11032 David Stevenson 2/5/2015 Re: Soft Limits Programming Issue [1 Attachment] DynoMotion 11034 Tom Kerekes 2/5/2015 Re: Soft Limits Programming Issue DynoMotion 11035 David Stevenson 2/5/2015 Re: Soft Limits Programming Issue DynoMotion 11036 David Stevenson 2/6/2015 Re: Soft Limits Programming Issue DynoMotion 11037 Tom Kerekes 2/6/2015 Re: Soft Limits Programming Issue